…ine#7890)

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

- Fix redesign/provider_rate_offset 2011 value: $78.40 → $24.40
  (was max OSS cap, not offset; SSA 2011 income limit $752.40 confirms)
- Fix redesign/max_oss/couple 2011 value: $396.80 → $156.80
  (SSA 2011 footnote b: couples treated as two individuals)
- Replace broken 404 Appendix A-12 URL in all 9 parameter files
- Update affected test expected values

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

Add protected/in_effect.yaml (false before 2024-07-01, true after)
to properly gate the Protected track instead of using $0 values as
sentinels. Formulas now use `if p.protected.in_effect:` to avoid
accessing Protected parameters in pre-2024 periods.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

Replace bare ssi_claim_is_joint with fl_oss_couple_rate_applies that
checks both spouses are is_ssi_eligible AND in a qualifying facility.
Also align eligibility with FAC 65A-2.033: use ssi > 0 (actual SSI
receipt per statute) instead of uncapped_ssi > 0, and allow Medicaid
facility residents to qualify via Group 2 (income standard).

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

- Update 404 Appendix A-12 URL in 3 variable files (2024-10 → 2025-05)
- Remove duplicate date entry in redesign/provider_rate_offset.yaml
- Remove value annotations from reference titles in max_oss files
- Fix descriptions: use allowed verbs and "this indicator" pattern
- Spell out PNA acronym in label

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

- Medicaid facility: Group 1 only (ssi > 0), no Group 2 path — FAC
  65A-2.036 defines no income standard for Medicaid facility residents
- Simplify fl_oss_couple_rate_applies: rely on ssi_claim_is_joint for
  Title XIX separation (see PolicyEngine#8003) instead of inline same_category check
- Add integration Cases 12-14: Medicaid facility negative path, couple
  with SSI equal-split, and earnings with SSI exclusions
- Fix couple_rate_applies Case 6: mixed ALF/Medicaid simulates fixed
  federal behavior per 20 CFR 416.1149

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

# Conflicts:
#	policyengine_us/parameters/gov/household/household_state_benefits.yaml
#	policyengine_us/variables/household/income/spm_unit/spm_unit_benefits.py

FAC 65A-2.032/.033/.036 (current) cover only ALF, AFCH, and MHRTF.
Medicaid facility is not an OSS coverage group. The $5/$10 supplement
in the 2011 SSA report reflects an older FL program structure that has
since been restructured; Medicaid institutional PNA is administered
separately from OSS.

Also: standardize Appendix A-12 URLs to the 2025-05 version; mark
FL OSS as complete in programs.yaml with variable: fl_oss.

Couple rate gating (P1):
- fl_oss_couple_rate_applies now requires both spouses on the same
  non-NONE program track. Appendix A-12 defines couple rates separately
  for Redesign and Protected; there is no mixed-track couple rate.
- Added integration Case 12 (mixed-track MHRTF couple) that pins
  provider rate, max OSS, and fl_oss to individual-rate values; locks
  down the original bug directly.

Protected track backdating (P2):
- The 2024-06 Appendix A-12 shows Protected Program Standards columns
  for Jan 2023 and Jan 2024, proving Protected took effect before the
  previously modeled Jul 2024 date.
- protected/in_effect.yaml: 2024-07-01 -> 2023-01-01.
- protected/provider_rate_offset.yaml: 2024-07-01 -> 2023-01-01 ($185).
- protected/max_oss: added 2023-01-01 values ($239 I, $478 C).
- couple_provider_rate_reduction.yaml: 2024-07-01 -> 2023-01-01 ($73).
- Redesign max_oss couple corrected from $386.80 to $368.80 for
  2024-07-01 (matches 2024-06 Appendix and the 2x-individual rule
  that holds for every other max_oss pair in both Appendices;
  $386.80 in the 2025-05 Appendix appears to be a typo).
- Every reference annotation now specifies which column / value each
  source document shows, so clicking each link lands on a PDF where
  the cited number is visibly present.
- Tests updated: edge_cases Cases 8, 12, 13, 20, 28; fl_oss_max_oss
  Case 3; integration Cases 2 and 10.

All 80 FL OSS tests pass.